Technique for Generating and/or Managing RNTIs

ABSTRACT

A wireless device is configured to determine a Random Access-Radio Network Temporary Identifier (RA-RNTI) for use in a radio network system. The wireless device comprises a first counter configured to be incremented after a pre-defined period of time and to be re-set when having reached a predefined first number, wherein the first counter counts a first count; a second counter configured to be incremented when the first counter reaches the predefined first number and to be re-set when having reached a predefined second number, wherein the second counter counts a second count; and a third counter configured to be incremented when the second counter reaches the predefined second number and to be re-set when having reached a predefined third number, wherein the third counter counts a third count. The wireless device is configured to determine an RA-RNTI at least based on the second count and the third count.

TECHNICAL FIELD

The present disclosure generally relates to radio network systems. Inparticular a technique for generating and managing Radio NetworkTemporary Identifiers, RNTIs, is described. The technique may beimplemented in the form of apparatuses, wireless terminals, networknodes, systems, methods and computer programs, to name a fewimplementations.

BACKGROUND

The 3^(rd) Generation Partnership Project (3GPP) Rel-13 defines new aradio access technology, named NB-IoT, see [1]. NB-IoT is primarilydefined for low-throughput, delay-tolerant applications, such as metersand sensors. It enables data rates of just 10's of kbps with 180 kHz ofbandwidth, and can provide deep coverage. NB-IoT can be deployed withinan existing Long Term Evolution (LTE) band, in guard-band between tworegular LTE carriers, or in standalone mode, which provides an easymigration path for the re-farmed GSM (2G/GPRS) spectrum.

NB-IoT technology occupies a frequency band of 180 kHz bandwidth, whichcorresponds to one resource block in LTE transmission. Due to thereduced channel bandwidth, most physical channels have been redesigned:NSSS/NPSS, NPBCH, NRS, NPDCCH (see FIG. 1).

Some of the use cases targeted by NB-IoT are:

-   -   Smart metering (electricity, gas and water)    -   Intruder alarms & fire alarms for homes & commercial properties    -   Smart city infrastructure such as street lamps or dustbins    -   Connected industrial appliances such as welding machines or air        compressors.

Different coverage extension levels have been defined to cope withdifferent radio conditions. There are typically three coverageenhancement (CE) levels, CE level 0 to CE level 2. CE level 0corresponds to normal coverage, and CE level 2 to the worst case, wherethe coverage is assumed to be very poor. The main impact of thedifferent CE levels is that the messages have to be repeated severaltimes especially for CE 2, see [2].

3GPP Rel-14 introduces further enhancements to support positioning,multi-cast, reduced latency and power consumption, and non-anchorcarrier operation in Rel-14, see [2].

Rel-15 aims to introduce a TDD version of NB-IoT. TDD spectrum alsoexists globally, including regulatory environments and operator marketswhere there is strong un-met demand for NB-IoT. In some cases thisdemand has existed since the early phases of the Rel-13 work. Therefore,Rel-15 is the right time to add TDD support into NB-IoT, afterestablishing what the needed targets in terms of coverage, latency, etc.should be.

TDD mode fundamentally differs from FDD mode. In FDD mode, separateuplink and downlink frames are used. However, in TDD mode, uplink anddownlink resources are allocated within the same frame. Some of thesub-frames are allocated for uplink whereas some are allocated fordownlink. In TDD mode different UL/DL configurations are provided asshown in the table of FIG. 2, see also [4](D=downlink/U=uplink/S=special field (e.g. DwPTS/UpPTS (Uplink/DownlinkPilot Time Slot)).

Random access is a radio network procedure involving the UE and a radioaccess node initiated by the UE to gain network access. It isessentially the same for both FDD and TDD. A temporary identifier,namely the RA-RNTI, is for example used on the PDCCH (Physical DownlinkControl Channel) when Random Access Response messages are transmitted bythe radio access node. It unambiguously identifies which time-frequencyresource was utilized by the Medium Access Control (MAC) entity of UE totransmit the Random Access Preamble message, see [3].

For NB-IoT FDD UEs, the RA-RNTI associated with the PRACH (PhysicalRandom Access Channel), in which the Random Access Preamble istransmitted, is computed as (see [3]):

$\begin{matrix}{{{RA}\text{-}{RNTI}} = {1 + {{floor}\mspace{11mu}\left( {{{SFN}\_{id}}/4} \right)} + {256*{carrier}_{-}id}}} & (1)\end{matrix}$

where SFN_id (sometimes also abbreviated as SFN hereinbelow) is theindex of the first radio frame of the specified PRACH and carrier_id isthe index of the UL carrier associated with the specified PRACH. Thecarrier_id of the anchor carrier is 0.

System Information Broadcast (SIB 2) is used to convey the NPRACH(NB-IoT PRACH) configurations to the UE. The configuration includesdetails regarding NPRACH resource, frequency location of the NPRACHresource, start time of the NPRACH resource etc.

The above RA-RNTI equation (1) for NB-IoT, which is based on the SystemFrame Number (SFN), may have a wrap around issue, for example in case oflimited resource availability and/or in case of a high number ofrepetitions needed for UEs located in an extended coverage area. Thiswrap around issue can lead to collisions among UE utilizing the sameRA-RNTI. Specifically, it can easily happen in an NB-IoT scenario(especially in TDD mode) that UEs have the same RA-RNTI because of awrap around of the SFN, as will now be discussed in greater detail.

The SFN counter counts from 0 to 1023 based upon the subframe numbercounter. This means that the subframe number counter counts from 0 to 9,which on increment every 10 msec. When the subframe number count reaches9, the subframe number counter is reset and the SFN counter isincremented. Based on this subframe number and system frame numberdefinitions, the longest time span without resetting SFN to 0 will be1024*10 msec (10.24 sec).

Assume, for example, that UE A at extended coverage uses subframe number5 for SFN 500 to send its random access. Thus, according to equation (1)and assuming that carrier_id=0, the following RA-RNTI will becalculated:

RA-RNTI = 1 + floor  (500/4) + 256 * 0 = 126

After having sent the Random Access Preamble message at subframe number5 for SFN 500, UE A happens to wait for a Random Access Response messagefrom the network. It may happen that SFN has wrapped around afterreaching 1023 and is back to again 500. UE A could have random accessrepetition needed for up to 128 times.

For NB-IoT FDD mode, one random access duration lasts for 6.4 ms; thusit can be 128*6.4˜=8 sec, which is shorter than the 10.24 sec discussedabove and thus generally avoids collision problems. For NB-IoT TDD mode,however, different UL and DL configurations are available; thus it couldhappen that the procedure takes longer either in UL or DL, and UE A maywait longer than 10.24 sec for the Random Access Response message fromthe network. Meanwhile, UE B, which is in good coverage, could use thesame RA-RNTI 126; thus there is a risk of collision.

Similarly, equation (1) provides 256 RA-RNTI values per carrier forNB-IoT FDD mode. For TDD mode, since it would take longer, 256 RA-RNTIwill not be sufficient as most of the RA-RNTI could be occupied (inuse).

It will be appreciated that similar problems can occur in radio networksystems different from NB-IoT that rely on a random access scheme.

SUMMARY

Accordingly, there is a need for a technique of generating and/ormanaging RNTIs, that avoids one or more disadvantages discussed above,or other disadvantages.

Certain aspects of the present disclosure and their embodiments mayprovide solutions to these or other challenges. Therefore, there are,proposed herein, various embodiments which address one or more of theissues disclosed herein.

According to a first aspect, a wireless device is provided that isconfigured to determine a Random Access-Radio Network TemporaryIdentifier, RA-RNTI, for use in a radio network system. The wirelessdevice comprises a first counter configured to be incremented after apre-defined period of time and to be re-set when having reached apredefined first number, wherein the first counter counts a first count;a second counter configured to be incremented when the first counterreaches the predefined first number and to be re-set when having reacheda predefined second number, wherein the second counter counts a secondcount; and a third counter configured to be incremented when the secondcounter reaches the predefined second number and to be re-set whenhaving reached a predefined third number, wherein the third countercounts a third count. The wireless device is configured to determine anRA-RNTI at least based on the second count and the third count.

The wireless device may be a user terminal (e.g., a smartphone, laptopor tablet computer) or an NB-IoT device (e.g., a sensor or sensorsystem). The wireless device may be configured to perform a randomaccess procedure, for example with the steps defined in [3].

The wireless device may be configured to determine the RA-RNTI byapplying one or more mathematical and/or bit-level operations on thesecond count and the third count and by using the result of these one ormore operations (e.g., expressed as a decimal integer value) as theRA-RNTI.

The first, second and third counters may hierarchically be realized on asubframe basis. The first counter may, for example, be a subframecounter. Each subframe may have a dedicated duration defined by thepredefined period of time (e.g., in the order of msec, such as 10 msec).The first counter may be configured to count from 0 to the predefinedfirst number (e.g., to 9). The corresponding first count could also beinterpreted as a subframe identifier (subframe_id). The second countermay be a system frame number counter, or SFN counter. The second countermay be configured to count from 0 to the predefined second number (e.g.,to 1023). The corresponding second count could also be interpreted as anSFN identifier (SFN_id), so SFN and SFN_id are used synonymously herein.The third counter may be a hyper frame counter, or HFN (sometimes alsodenoted H-SFN) counter. The third counter may be configured to countfrom 0 to a predefined third number (e.g., to 1023). The correspondingthird count could also be interpreted as an HFN identifier (HFN_id), soHFN and HFN_id are used synonymously herein.

The first, second and third counts may correspond to the subframenumber, the SFN number and the HFN number, respectively, as presentlydefined, or as will be defined, in 3GPP specifications (e.g., forNB-IoT), such as 3GPP Rel-13, Rel-14, Rel-15 and later.

The RA-RNTI may identify (e.g., determine) at least a time resource fortransmission of a random access request message by the wireless device.The time resource may be represented in terms of one or more of asubframe number, an SFN number and an HFN number. In particular, thesecond count (e.g., SFN_id) and the third count (e.g., HFN_ID) as usedfor determining the RA-RNTI may be indicative of the first radio frameof a specified PRACH. In addition, the RA-RNTI may identify a frequencyresource for transmission of a random access request message by thewireless device (e.g., in terms of a carrier identifier). In such acase, determination of the RA-RNTI may additionally be based on an indexof an uplink carrier associated with the specified PRACH

The random access request message may be a Random Access Preamblemessage (e.g., as defined in 3GPP specifications such as 3GPP Rel-13,Rel-14, Rel-15, or later releases, see also [3] for more details). TheRandom Access Preamble message may be answered from the network side bya random access response message also associated with (e.g., including)the RA-RNTI determined by the wireless device. The random accessmessages may be sent on a RACH, including PRACH and NPRACH. The randomaccess messages may generally conform to 3GPP specifications (e.g., forNB-IoT), such as 3GPP Rel-13, Rel-14, Rel-15 and later (see, e.g., [3]for more details).

The wireless device may be configured to determine the RA-RNTIresponsive to a decision that a random access is to be performed. Forexample, in preparation for transmission of a random access requestmessage (such as a random Access Preamble message), the wireless devicemay trigger identification (e.g., determination) of a time (and,optionally, a frequency) resource for the transmission of the randomaccess message. The RA-RNTI may then in a next step be determined on thebasis of the identified time (and, optionally, frequency) resource. Thetime resource may be indicated by the second count and the third countas underlying the RA-RNTI determination.

The wireless device may be configured to determine a number x ofdifferent RA-RNTIs that exceeds a constant a plus the floor of thepre-defined second number y divided by a constant z so that

x > a + floor  (y/z).

In some variants, a=1 or a=1 plus 256 times a maximum uplink carrierindex. The uplink carrier index may be associated with a particularfrequency resource (e.g., for transmission of the random accessmessage). Different frequency resources (e.g., carriers) may havedifferent indices, including the maximum uplink carrier index as thehighest index (e.g., the largest integer number) of all such indices. Insome variants, y=1023. In some variants, z=4. (see, e.g., [3]).

The number x of different RA-RNTIs may exceed 260 or 520 or 1040 or 2080or 5150. The number x of different RA-RNTIs may exceed the secondpredefined number. It may equal the product of the first predefinednumber and the third predefined number (e.g., in terms of y) or it mayexceed the second predefined number but be less than that product. Inthe latter case, a further parameter may enter the RA-RNTI determinationto render the resulting number space smaller than that product (e.g., interms of a quotient z).

The wireless device may be configured to determine the RN-RNTI based ona mathematical formula that includes both the second count and the thirdcount. As an example, the wireless device may be configured to determinethe RN-RNTI based on a+floor (y/z), for example according to

RA-RNTI = a + floor  (y/z),

wherein

a is an integer including one of: 0; 1; a number>1; and 1+ an integermultiple of an uplink carrier index; y is an integer determined on thebasis of both the second count and the third count; and z is an integerincluding one of: 1 and a number>1. In some cases, y is configured toexceed the predefined second number.

In some cases, the wireless device is configured to determine theRN-RNTI based on

1 + floor  ((b + (c + 1) * mod (d, e))/z) + f,

for example according to

RA-RNTI = 1 + floor  ((b + (c + 1) * mod (d, e))/z) + f,

wherein

b is the second count; c is the second predefined number; d is the thirdcount; e is an integer including 1; z is an integer including 1; and fis an integer including 0, 1 or a number>1. In some variants, f may bedefined as follows

f = (c + 1) * e/z * carrier⁻id,

wherein

carrier_id is an uplink carrier index.

The wireless device may be configured to determine the RA-RNTI based ona bit-level operation applied to binary representations of the secondcount and the third count. As an example, the wireless device may beconfigured to determine the RA-RNTI based on a binary number that hasbeen generated by appending one or more bits of a binary representationof the third count to a binary representation of the second count. As amore detailed example, one or more least significant bits of the binaryrepresentation of the third count may be appended (e.g., prepended) toat least a portion of the binary representation of the second count(e.g., to the most significant bit side of that binary representation).The decimal integer corresponding to the resulting binary number may beused as the RA-RNTI.

The wireless device may be configured to generate a random accessrequest message in accordance with the RA-RNTI and send the randomaccess request message towards an access network. The random accessrequest message, such as a Random Access Preamble message, may be senton the time (and, optionally, frequency) resource corresponding to theRA-RNTI. The RA-RNTI itself may or may not be included in the randomaccess request message.

The wireless device may be configured to additionally, or in thealternative, identify a random access response message from the accessnetwork associated with the RA-RNTI. The RA-RNTI itself may or may notbe included in the random access response message.

The wireless device may be configured to determine the RA-RNTI based onan expression that yields a uniform distribution of RA-RNTI values.

In one exemplary realization, the above parameters are set and definedas follows

-   -   b is a system frame number;    -   c=1023;    -   d is a hyper frame number;    -   e=2 or 4; and    -   z=4.

The wireless device may be configured to determine the RN-RNTI accordingto

RA-RNTI = 1 + floor  ((b/4) + 1024 * mod (d, 2),

wherein

-   -   b is the second count (e.g., SFN);    -   d is the third count (e.g., HFN).

The wireless device may be a Narrowband Internet of Things UserEquipment, NB-IoT UE, configured to determine the RA-RNTI for a TimeDivision Duplex, TDD, mode.

According to a further aspect, an access network node configured todetermine a Random Access-Radio Network Temporary Identifier, RA-RNTI,for use in a radio network system is provided. The access network nodecomprises a first counter configured to be incremented after apre-defined period of time and to be re-set when having reached apredefined first number, wherein the first counter counts a first count;a second counter configured to be incremented when the first counterreaches the predefined first number and to be re-set when having reacheda predefined second number, wherein the second counter counts a secondcount; and a third counter configured to be incremented when the secondcounter reaches the predefined second number and to be re-set whenhaving reached a predefined third number, wherein the third countercounts a third count. The access network node further comprises aninterface configured to receive a random access message from a wirelessdevice and is configured to determine an RA-RNTI associated with therandom access message based on the second count and the third count atthe time when the random access message was received.

Determination of the RA-RNTI may be based on the same principle (e.g.,based on the same mathematical formula or operations or based on thesame bit-level operations) as discussed above and below in regard to thewireless device.

The access network node may be configured to generate a random accessresponse message in accordance with (e.g., that includes) the RA-RNTIand send the random access response message to the wireless device. Therandom access response message may be generate in response to receipt ofa random access request message (e.g., a Random Access Preamble message)from the wireless devices. The random access messages may be sent on aRandom Access Channel (RACH), including PRACH and NPRACH.

The access network node may be configured to manage (e.g., one or moreof determine, use, compare, send, etc.) a first RNTI type comprising anumber (e.g., a given set) of designated RA-RNTIs available for use inthe radio network system and at least one second RNTI type differentfrom the first type. The access network node may be configured todetermine, based on a priori-knowledge, one or more designated RA-RNTIsavailable but unused in the radio network system. The access networknode may be configured to allocate the one or more unused designatedRA-RNTIs to the second RNTI type.

The identifiers (designated RA-RNTIs) thus allocated to the second RNTItype may subsequently be assigned by the access network node to wirelessdevices.

Exemplary second RNTI types include a Cell-RNTI (C-RNTI) type and atemporary C-RNTI type. The a priori-knowledge may relate to informationabout which RA-RNTIs within a given RA-RNTI set will remain unused inview of system constraints. The a prior-knowledge may relate tocommunication opportunities on a transmission channel (e.g., the RACH,including the PRACH and/or NPRACH). In particular, the a prior-knowledgemay relate to one or more RACH configurations that are not valid, andthus unusable, for random access request messages by the wirelessdevice. Of course, such designate RA-RNTIs will never be used by anywireless device and, thus, remain unnecessarily occupied. In case theone or more RACH configurations change at a later point in time, thedetermination and allocation steps may be repeated. In such a case, forexample C-RNTIs or temporary C-RNTIs may have to be revoked and/orre-allocated to RA-RNTIs. Alternatively, or in addition, previouslyallocated identifiers (RNTIs) as needed for a new RACH configuration maybe reserved (e.g., not allocated in regard to the second RNTI type) asthey become free (e.g., as connections are released)

The given set of designated RA-RNTIs may be defined by an underlyingRA-RNTI determination principle as discussed above and below (e.g., by amathematical formula or mathematical operations or by bit-leveloperations).

By allocating (or, actually, re-allocating or re-mapping) an identifier(e.g., an integer number) originally designated as (or allocated ormapped to) a RA-RNTI to another RNTI type, such as using that number asone of a C-RNTI and a temporary C-RNTI, the identifier space for theother RNTI type can be increased. As such, a potential decrease of theidentifier space for the other RNTI type that results from the desiredincrease of the identifier space for the RA-RNTI type can at leastpartially be compensated.

The access network node may be configured to determine the RN-RNTIaccording to

RA-RNTI = 1 + floor  ((b/4) + 1024* mod (d, 2),

wherein

-   -   b is the second count (e.g., SFN);    -   d is the third count (e.g., HFN).

The access network node may be configured to determine the RA-RNTI for aTime Division Duplex, TDD, mode.

In view of the above, there is also provided is an access network nodefor managing Radio Network Temporary Identifiers, RNTIs, for use in aradio network system, the RNTIs belonging to a first RNTI typecomprising a number of designated Random Access-, RA-, RNTIs and asecond RNTI type different from the first type. The access network nodeis configured to determine, based on a priori-knowledge, one or moredesignated RA-RNTIs available but unused in the radio network system;and to allocate the one or more unused designated RA-RNTIs to the secondRNTI type.

Further provided is a radio network system including one or more of thewireless devices discussed herein and/or at least one access networknode discussed herein.

The radio network system may be configured to operate in a Time DivisionDuplex, TDD, mode. The radio network system may further be configured toalso operate in a Frequency Division Duplex, FDD, mode. The radionetwork system may conform to 3GPP Rel-13, Rel-14, Rel-15 or higher. Theradio network system may be configured to conform to 3GPP NB-IoTspecifications.

Also provided is a method of determining a Random Access-Radio NetworkTemporary Identifier, RA-RNTI, for use in a radio network system, themethod being performed by a wireless device and comprising operating afirst counter configured to be incremented after a pre-defined period oftime and to be re-set when having reached a predefined first number,wherein the first counter counts a first count; operating a secondcounter configured to be incremented when the first counter reaches thepredefined first number and to be re-set when having reached apredefined second number, wherein the second counter counts a secondcount; and operating a third counter configured to be incremented whenthe second counter reaches the predefined second number and to be re-setwhen having reached a predefined third number, wherein the third countercounts a third count; and determining an RA-RNTI at least based on thesecond count and the third count.

Further provided is a method of determining a Random Access-RadioNetwork Temporary Identifier, RA-RNTI, for use in a radio networksystem, the method being performed by an access network node andcomprising operating a first counter configured to be incremented aftera pre-defined period of time and to be re-set when having reached apredefined first number, wherein the first counter counts a first count;operating a second counter configured to be incremented when the firstcounter reaches the predefined first number and to be re-set when havingreached a predefined second number, wherein the second counter counts asecond count; operating a third counter configured to be incrementedwhen the second counter reaches the predefined second number and to bere-set when having reached a predefined third number, wherein the thirdcounter counts a third count; receiving a random access message from awireless device; and determining an RA-RNTI associated with the randomaccess message based on the second count and the third count at the timewhen the random access message was received.

Still further provided is a method of managing Radio Network TemporaryIdentifiers, RNTIs, for use in a radio network system, the RNTIsbelonging a first RNTI type comprising a number of designated RandomAccess-, RA-, RNTIs and a second RNTI type different from the firsttype, wherein the method comprises determining, based on apriori-knowledge, one or more designated RA-RNTIs available but unusedin the radio network system; and allocating the one or more unuseddesignated RA-RNTIs to the second RNTI type.

The methods presented herein may comprises further steps as explainedabove and below.

Also provided is a computer program product comprising software codeportions for performing the steps of the methods presented herein whenexecuted on a computing device. The computer program product may bestored on a computer-readable recording medium, such as a semiconductormemory, a CD-ROM, etc.

Also provided is an apparatus comprising a processor and a memorycoupled to the processor, wherein the memory stores program code thatperforms one of the methods presented herein when executed by theprocessor.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings illustrate exemplary scenarios of where and how the presentdisclosure can be implemented. In more detail,

FIG. 1 illustrates an NB-IoT Physical Resource Block, PRB, embodiment;

FIG. 2 illustrates a TDD embodiment;

FIG. 3 illustrates a system embodiment with wireless device and networknode embodiments;

FIGS. 4A, B illustrate wireless device embodiments;

FIG. 5 illustrates a method embodiment in regard to a wireless device;

FIGS. 6A, B illustrates network node embodiments;

FIG. 7 illustrates a method embodiment in regard to a network node; and

FIGS. 8A, B illustrate exemplary distributions of RA-RNTI values.

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described ingreater detail with reference to the accompanying drawings. Otherembodiments, however, are contained within the scope of the subjectmatter disclosed herein, and the disclosed subject matter should not beconstrued as limited to only the embodiments set forth herein; rather,these embodiments are provided by way of example to convey the scope ofthe present disclosure to those skilled in the art.

Although the subject matter described herein may be implemented in anyappropriate type of system using any suitable components, theembodiments disclosed herein are described in relation to a wirelessnetwork, such as the example wireless network illustrated in FIG. 3. Forsimplicity, the wireless network of FIG. 3 only depicts network QQ106,network nodes QQ160 and QQ160 b, and WDs QQ110, QQ110 b, and QQ110 c. Inpractice, a wireless network may further include any additional elementssuitable to support communication between wireless devices or between awireless device and another communication device, such as a landlinetelephone, a service provider, or any other network node or end device.Of the illustrated components, network node QQ160 and wireless device(WD) QQ110 are depicted with additional detail. The wireless network mayprovide communication and other types of services to one or morewireless devices to facilitate the wireless devices' access to and/oruse of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type ofcommunication, telecommunication, data, cellular, and/or radio networkor other similar type of system.

In some embodiments, the wireless network may be configured to operateaccording to specific standards or other types of predefined rules orprocedures. Thus, particular embodiments of the wireless network mayimplement communication standards, such as Global System for MobileCommunications (GSM), Universal Mobile Telecommunications System (UMTS),Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5Gstandards including in particular NB-IoT; wireless local area network(WLAN) standards, such as the IEEE 802.11 standards; and/or any otherappropriate wireless communication standard, such as the WorldwideInteroperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/orZigBee standards.

Network QQ106 may comprise one or more backhaul networks, core networks,IP networks, public switched telephone networks (PSTNs), packet datanetworks, optical networks, wide-area networks (WANs), local areanetworks (LANs), wireless local area networks (WLANs), wired networks,wireless networks, metropolitan area networks, and other networks toenable communication between devices.

Network node QQ160 and WD QQ110 comprise various components described inmore detail below. These components work together in order to providenetwork node and/or wireless device functionality, such as providingwireless connections in a wireless network. In different embodiments,the wireless network may comprise any number of wired or wirelessnetworks, network nodes, base stations, controllers, wireless devices,relay stations, and/or any other components or systems that mayfacilitate or participate in the communication of data and/or signalswhether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured,arranged and/or operable to communicate directly or indirectly with awireless device and/or with other network nodes or equipment in thewireless network to enable and/or provide wireless access to thewireless device and/or to perform other functions (e.g., administration)in the wireless network. Examples of network nodes include, but are notlimited to, access points (APs) (e.g., radio access points), basestations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs(eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based onthe amount of coverage they provide (or, stated differently, theirtransmit power level) and may then also be referred to as femto basestations, pico base stations, micro base stations, or macro basestations. A base station may be a relay node or a relay donor nodecontrolling a relay. A network node may also include one or more (orall) parts of a distributed radio base station such as centralizeddigital units and/or remote radio units (RRUs), sometimes referred to asRemote Radio Heads (RRHs). Such remote radio units may or may not beintegrated with an antenna as an antenna integrated radio. Parts of adistributed radio base station may also be referred to as nodes in adistributed antenna system (DAS). Yet further examples of network nodesinclude multi-standard radio (MSR) equipment such as MSR BSs, networkcontrollers such as radio network controllers (RNCs) or base stationcontrollers (BSCs), base transceiver stations (BTSs), transmissionpoints, transmission nodes, multi-cell/multicast coordination entities(MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SONnodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.

As another example, a network node may be a virtual network node asdescribed in more detail below. More generally, however, network nodesmay represent any suitable device (or group of devices) capable,configured, arranged, and/or operable to enable and/or provide awireless device with access to the wireless network or to provide someservice to a wireless device that has accessed the wireless network.

In FIG. 3, network node QQ160 includes processing circuitry QQ170,device readable medium QQ180, interface QQ190, auxiliary equipmentQQ184, power source QQ186, power circuitry QQ187, and antenna QQ162.Although network node QQ160 illustrated in the example wireless networkof FIG. 3 may represent a device that includes the illustratedcombination of hardware components, other embodiments may comprisenetwork nodes with different combinations of components. It is to beunderstood that a network node comprises any suitable combination ofhardware and/or software needed to perform the tasks, features,functions and methods disclosed herein. Moreover, while the componentsof network node QQ160 are depicted as single boxes located within alarger box, or nested within multiple boxes, in practice, a network nodemay comprise multiple different physical components that make up asingle illustrated component (e.g., device readable medium QQ180 maycomprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node QQ160 may be composed of multiple physicallyseparate components (e.g., a NodeB component and a RNC component, or aBTS component and a BSC component, etc.), which may each have their ownrespective components. In certain scenarios in which network node QQ160comprises multiple separate components (e.g., BTS and BSC components),one or more of the separate components may be shared among severalnetwork nodes. For example, a single RNC may control multiple NodeB's.In such a scenario, each unique NodeB and RNC pair, may in someinstances be considered a single separate network node. In someembodiments, network node QQ160 may be configured to support multipleradio access technologies (RATs). In such embodiments, some componentsmay be duplicated (e.g., separate device readable medium QQ180 for thedifferent RATs) and some components may be reused (e.g., the sameantenna QQ162 may be shared by the RATs). Network node QQ160 may alsoinclude multiple sets of the various illustrated components fordifferent wireless technologies integrated into network node QQ160, suchas, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wirelesstechnologies. These wireless technologies may be integrated into thesame or different chip or set of chips and other components withinnetwork node QQ160.

Processing circuitry QQ170 is configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being provided by a network node. These operationsperformed by processing circuitry QQ170 may include processinginformation obtained by processing circuitry QQ170 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedin the network node, and/or performing one or more operations based onthe obtained information or converted information, and as a result ofsaid processing making a determination.

Processing circuitry QQ170 may comprise a combination of one or more ofa microprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software and/or encoded logicoperable to provide, either alone or in conjunction with other networknode QQ160 components, such as device readable medium QQ180, networknode QQ160 functionality. For example, processing circuitry QQ170 mayexecute instructions stored in device readable medium QQ180 or in memorywithin processing circuitry QQ170. Such functionality may includeproviding any of the various wireless features, functions, or benefitsdiscussed herein. In some embodiments, processing circuitry QQ170 mayinclude a system on a chip (SOC).

In some embodiments, processing circuitry QQ170 may include one or moreof radio frequency (RF) transceiver circuitry QQ172 and basebandprocessing circuitry QQ174. In some embodiments, radio frequency (RF)transceiver circuitry QQ172 and baseband processing circuitry QQ174 maybe on separate chips (or sets of chips), boards, or units, such as radiounits and digital units. In alternative embodiments, part or all of RFtransceiver circuitry QQ172 and baseband processing circuitry QQ174 maybe on the same chip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality describedherein as being provided by a network node, base station, eNB or othersuch network device may be performed by processing circuitry QQ170executing instructions stored on device readable medium QQ180 or memorywithin processing circuitry QQ170. In alternative embodiments, some orall of the functionality may be provided by processing circuitry QQ170without executing instructions stored on a separate or discrete devicereadable medium, such as in a hard-wired manner. In any of thoseembodiments, whether executing instructions stored on a device readablestorage medium or not, processing circuitry QQ170 can be configured toperform the described functionality. The benefits provided by suchfunctionality are not limited to processing circuitry QQ170 alone or toother components of network node QQ160, but are enjoyed by network nodeQQ160 as a whole, and/or by end users and the wireless networkgenerally.

Device readable medium QQ180 may comprise any form of volatile ornon-volatile computer readable memory including, without limitation,persistent storage, solid-state memory, remotely mounted memory,magnetic media, optical media, random access memory (RAM), read-onlymemory (ROM), mass storage media (for example, a hard disk), removablestorage media (for example, a flash drive, a Compact Disk (CD) or aDigital Video Disk (DVD)), and/or any other volatile or non-volatile,non-transitory device readable and/or computer-executable memory devicesthat store information, data, and/or instructions that may be used byprocessing circuitry QQ170. Device readable medium QQ180 may store anysuitable instructions, data or information, including a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry QQ170 and, utilized by network node QQ160.Device readable medium QQ180 may be used to store any calculations madeby processing circuitry QQ170 and/or any data received via interfaceQQ190. In some embodiments, processing circuitry QQ170 and devicereadable medium QQ180 may be considered to be integrated.

Interface QQ190 is used in the wired or wireless communication ofsignaling and/or data between network node QQ160, network QQ106, and/orWDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s)QQ194 to send and receive data, for example to and from network QQ106over a wired connection. Interface QQ190 also includes radio front endcircuitry QQ192 that may be coupled to, or in certain embodiments a partof, antenna QQ162. Radio front end circuitry QQ192 comprises filtersQQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may beconnected to antenna QQ162 and processing circuitry QQ170. Radio frontend circuitry may be configured to condition signals communicatedbetween antenna QQ162 and processing circuitry QQ170. Radio front endcircuitry QQ192 may receive digital data that is to be sent out to othernetwork nodes or WDs via a wireless connection. Radio front endcircuitry QQ192 may convert the digital data into a radio signal havingthe appropriate channel and bandwidth parameters using a combination offilters QQ198 and/or amplifiers QQ196. The radio signal may then betransmitted via antenna QQ162. Similarly, when receiving data, antennaQQ162 may collect radio signals which are then converted into digitaldata by radio front end circuitry QQ192. The digital data may be passedto processing circuitry QQ170. In other embodiments, the interface maycomprise different components and/or different combinations ofcomponents.

In certain alternative embodiments, network node QQ160 may not includeseparate radio front end circuitry QQ192, instead, processing circuitryQQ170 may comprise radio front end circuitry and may be connected toantenna QQ162 without separate radio front end circuitry QQ192.Similarly, in some embodiments, all or some of RF transceiver circuitryQQ172 may be considered a part of interface QQ190. In still otherembodiments, interface QQ190 may include one or more ports or terminalsQQ194, radio front end circuitry QQ192, and RF transceiver circuitryQQ172, as part of a radio unit (not shown), and interface QQ190 maycommunicate with baseband processing circuitry QQ174, which is part of adigital unit (not shown).

Antenna QQ162 may include one or more antennas, or antenna arrays,configured to send and/or receive wireless signals. Antenna QQ162 may becoupled to radio front end circuitry QQ190 and may be any type ofantenna capable of transmitting and receiving data and/or signalswirelessly. In some embodiments, antenna QQ162 may comprise one or moreomni-directional, sector or panel antennas operable to transmit/receiveradio signals between, for example, 2 GHz and 66 GHz. Anomni-directional antenna may be used to transmit/receive radio signalsin any direction, a sector antenna may be used to transmit/receive radiosignals from devices within a particular area, and a panel antenna maybe a line of sight antenna used to transmit/receive radio signals in arelatively straight line. In some instances, the use of more than oneantenna may be referred to as MIMO. In certain embodiments, antennaQQ162 may be separate from network node QQ160 and may be connectable tonetwork node QQ160 through an interface or port.

Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may beconfigured to perform any receiving operations and/or certain obtainingoperations described herein as being performed by a network node. Anyinformation, data and/or signals may be received from a wireless device,another network node and/or any other network equipment. Similarly,antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may beconfigured to perform any transmitting operations described herein asbeing performed by a network node. Any information, data and/or signalsmay be transmitted to a wireless device, another network node and/or anyother network equipment.

Power circuitry QQ187 may comprise, or be coupled to, power managementcircuitry and is configured to supply the components of network nodeQQ160 with power for performing the functionality described herein.Power circuitry QQ187 may receive power from power source QQ186. Powersource QQ186 and/or power circuitry QQ187 may be configured to providepower to the various components of network node QQ160 in a form suitablefor the respective components (e.g., at a voltage and current levelneeded for each respective component). Power source QQ186 may either beincluded in, or external to, power circuitry QQ187 and/or network nodeQQ160. For example, network node QQ160 may be connectable to an externalpower source (e.g., an electricity outlet) via an input circuitry orinterface such as an electrical cable, whereby the external power sourcesupplies power to power circuitry QQ187. As a further example, powersource QQ186 may comprise a source of power in the form of a battery orbattery pack which is connected to, or integrated in, power circuitryQQ187. The battery may provide backup power should the external powersource fail. Other types of power sources, such as photovoltaic devices,may also be used.

Alternative embodiments of network node QQ160 may include additionalcomponents beyond those shown in FIG. 3 that may be responsible forproviding certain aspects of the network node's functionality, includingany of the functionality described herein and/or any functionalitynecessary to support the subject matter described herein. For example,network node QQ160 may include user interface equipment to allow inputof information into network node QQ160 and to allow output ofinformation from network node QQ160. This may allow a user to performdiagnostic, maintenance, repair, and other administrative functions fornetwork node QQ160.

As used herein, wireless device (WD) refers to a device capable,configured, arranged and/or operable to communicate wirelessly withnetwork nodes and/or other wireless devices. Unless otherwise noted, theterm WD may be used interchangeably herein with user equipment (UE).Communicating wirelessly may involve transmitting and/or receivingwireless signals using electromagnetic waves, radio waves, infraredwaves, and/or other types of signals suitable for conveying informationthrough air. In some embodiments, a WD may be configured to transmitand/or receive information without direct human interaction. Forinstance, a WD may be designed to transmit information to a network on apredetermined schedule, when triggered by an internal or external event,or in response to requests from the network. Examples of a WD include,but are not limited to, a smart phone, a mobile phone, a cell phone, avoice over IP (VoIP) phone, a wireless local loop phone, a desktopcomputer, a personal digital assistant (PDA), a wireless cameras, agaming console or device, a music storage device, a playback appliance,a wearable terminal device, a wireless endpoint, a mobile station, atablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mountedequipment (LME), a smart device, a wireless customer-premise equipment(CPE), a vehicle-mounted wireless terminal device, etc. A WD may supportdevice-to-device (D2D) communication, for example by implementing a 3GPPstandard for sidelink communication, vehicle-to-vehicle (V2V),vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may inthis case be referred to as a D2D communication device.

As yet another specific example, in an Internet of Things (IoT)scenario, a WD may represent a machine or other device that performsmonitoring and/or measurements, and transmits the results of suchmonitoring and/or measurements to another WD and/or a network node. TheWD may in this case be a machine-to-machine (M2M) device, which may in a3GPP context be referred to as an MTC device. As one particular example,the WD may be a UE implementing the 3GPP narrow band internet of things(NB-IoT) standard. Particular examples of such machines or devices aresensors, metering devices such as power meters, industrial machinery, orhome or personal appliances (e.g. refrigerators, televisions, etc.),personal wearables (e.g., watches, fitness trackers, etc.). In otherscenarios, a WD may represent a vehicle or other equipment that iscapable of monitoring and/or reporting on its operational status orother functions associated with its operation. A WD as described abovemay represent the endpoint of a wireless connection, in which case thedevice may be referred to as a wireless terminal. Furthermore, a WD asdescribed above may be mobile, in which case it may also be referred toas a mobile device or a mobile terminal.

As illustrated, wireless device QQ110 includes antenna QQ111, interfaceQQ114, processing circuitry QQ120, device readable medium QQ130, userinterface equipment QQ132, auxiliary equipment QQ134, power source QQ136and power circuitry QQ137. WD QQ110 may include multiple sets of one ormore of the illustrated components for different wireless technologiessupported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi,WiMAX, or Bluetooth wireless technologies, just to mention a few. Thesewireless technologies may be integrated into the same or different chipsor set of chips as other components within WD QQ110.

Antenna QQ111 may include one or more antennas or antenna arrays,configured to send and/or receive wireless signals, and is connected tointerface QQ114. In certain alternative embodiments, antenna QQ111 maybe separate from WD QQ110 and be connectable to WD QQ110 through aninterface or port. Antenna QQ111, interface QQ114, and/or processingcircuitry QQ120 may be configured to perform any receiving ortransmitting operations described herein as being performed by a WD. Anyinformation, data and/or signals may be received from a network nodeand/or another WD. In some embodiments, radio front end circuitry and/orantenna QQ111 may be considered an interface.

As illustrated, interface QQ114 comprises radio front end circuitryQQ112 and antenna QQ111. Radio front end circuitry QQ112 comprise one ormore filters QQ118 and amplifiers QQ116. Radio front end circuitry QQ114is connected to antenna QQ111 and processing circuitry QQ120, and isconfigured to condition signals communicated between antenna QQ111 andprocessing circuitry QQ120. Radio front end circuitry QQ112 may becoupled to or a part of antenna QQ111. In some embodiments, WD QQ110 maynot include separate radio front end circuitry QQ112; rather, processingcircuitry QQ120 may comprise radio front end circuitry and may beconnected to antenna QQ111. Similarly, in some embodiments, some or allof RF transceiver circuitry QQ122 may be considered a part of interfaceQQ114. Radio front end circuitry QQ112 may receive digital data that isto be sent out to other network nodes or WDs via a wireless connection.Radio front end circuitry QQ112 may convert the digital data into aradio signal having the appropriate channel and bandwidth parametersusing a combination of filters QQ118 and/or amplifiers QQ116. The radiosignal may then be transmitted via antenna QQ111. Similarly, whenreceiving data, antenna QQ111 may collect radio signals which are thenconverted into digital data by radio front end circuitry QQ112. Thedigital data may be passed to processing circuitry QQ120. In otherembodiments, the interface may comprise different components and/ordifferent combinations of components.

Processing circuitry QQ120 may comprise a combination of one or more ofa microprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software, and/or encoded logicoperable to provide, either alone or in conjunction with other WD QQ110components, such as device readable medium QQ130, WD QQ110functionality. Such functionality may include providing any of thevarious wireless features or benefits discussed herein. For example,processing circuitry QQ120 may execute instructions stored in devicereadable medium QQ130 or in memory within processing circuitry QQ120 toprovide the functionality disclosed herein.

As illustrated, processing circuitry QQ120 includes one or more of RFtransceiver circuitry QQ122, baseband processing circuitry QQ124, andapplication processing circuitry QQ126. In other embodiments, theprocessing circuitry may comprise different components and/or differentcombinations of components. In certain embodiments processing circuitryQQ120 of WD QQ110 may comprise a SOC. In some embodiments, RFtransceiver circuitry QQ122, baseband processing circuitry QQ124, andapplication processing circuitry QQ126 may be on separate chips or setsof chips. In alternative embodiments, part or all of baseband processingcircuitry QQ124 and application processing circuitry QQ126 may becombined into one chip or set of chips, and RF transceiver circuitryQQ122 may be on a separate chip or set of chips. In still alternativeembodiments, part or all of RF transceiver circuitry QQ122 and basebandprocessing circuitry QQ124 may be on the same chip or set of chips, andapplication processing circuitry QQ126 may be on a separate chip or setof chips. In yet other alternative embodiments, part or all of RFtransceiver circuitry QQ122, baseband processing circuitry QQ124, andapplication processing circuitry QQ126 may be combined in the same chipor set of chips. In some embodiments, RF transceiver circuitry QQ122 maybe a part of interface QQ114. RF transceiver circuitry QQ122 maycondition RF signals for processing circuitry QQ120.

In certain embodiments, some or all of the functionality describedherein as being performed by a WD may be provided by processingcircuitry QQ120 executing instructions stored on device readable mediumQQ130, which in certain embodiments may be a computer-readable storagemedium. In alternative embodiments, some or all of the functionality maybe provided by processing circuitry QQ120 without executing instructionsstored on a separate or discrete device readable storage medium, such asin a hard-wired manner. In any of those particular embodiments, whetherexecuting instructions stored on a device readable storage medium ornot, processing circuitry QQ120 can be configured to perform thedescribed functionality. The benefits provided by such functionality arenot limited to processing circuitry QQ120 alone or to other componentsof WD QQ110, but are enjoyed by WD QQ110 as a whole, and/or by end usersand the wireless network generally.

Processing circuitry QQ120 may be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being performed by a WD. These operations, asperformed by processing circuitry QQ120, may include processinginformation obtained by processing circuitry QQ120 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedby WD QQ110, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Device readable medium QQ130 may be operable to store a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry QQ120. Device readable medium QQ130 may includecomputer memory (e.g., Random Access Memory (RAM) or Read Only Memory(ROM)), mass storage media (e.g., a hard disk), removable storage media(e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or anyother volatile or non-volatile, non-transitory device readable and/orcomputer executable memory devices that store information, data, and/orinstructions that may be used by processing circuitry QQ120. In someembodiments, processing circuitry QQ120 and device readable medium QQ130may be considered to be integrated.

User interface equipment QQ132 may provide components that allow for ahuman user to interact with WD QQ110. Such interaction may be of manyforms, such as visual, audial, tactile, etc. User interface equipmentQQ132 may be operable to produce output to the user and to allow theuser to provide input to WD QQ110. The type of interaction may varydepending on the type of user interface equipment QQ132 installed in WDQQ110. For example, if WD QQ110 is a smart phone, the interaction may bevia a touch screen; if WD QQ110 is a smart meter, the interaction may bethrough a screen that provides usage (e.g., the number of gallons used)or a speaker that provides an audible alert (e.g., if smoke isdetected). User interface equipment QQ132 may include input interfaces,devices and circuits, and output interfaces, devices and circuits. Userinterface equipment QQ132 is configured to allow input of informationinto WD QQ110, and is connected to processing circuitry QQ120 to allowprocessing circuitry QQ120 to process the input information. Userinterface equipment QQ132 may include, for example, a microphone, aproximity or other sensor, keys/buttons, a touch display, one or morecameras, a USB port, or other input circuitry. User interface equipmentQQ132 is also configured to allow output of information from WD QQ110,and to allow processing circuitry QQ120 to output information from WDQQ110. User interface equipment QQ132 may include, for example, aspeaker, a display, vibrating circuitry, a USB port, a headphoneinterface, or other output circuitry. Using one or more input and outputinterfaces, devices, and circuits, of user interface equipment QQ132, WDQQ110 may communicate with end users and/or the wireless network, andallow them to benefit from the functionality described herein.

Auxiliary equipment QQ134 is operable to provide more specificfunctionality which may not be generally performed by WDs. This maycomprise specialized sensors for doing measurements for variouspurposes, interfaces for additional types of communication such as wiredcommunications etc. The inclusion and type of components of auxiliaryequipment QQ134 may vary depending on the embodiment and/or scenario.

Power source QQ136 may, in some embodiments, be in the form of a batteryor battery pack. Other types of power sources, such as an external powersource (e.g., an electricity outlet), photovoltaic devices or powercells, may also be used. WD QQ110 may further comprise power circuitryQQ137 for delivering power from power source QQ136 to the various partsof WD QQ110 which need power from power source QQ136 to carry out anyfunctionality described or indicated herein. Power circuitry QQ137 mayin certain embodiments comprise power management circuitry. Powercircuitry QQ137 may additionally or alternatively be operable to receivepower from an external power source; in which case WD QQ110 may beconnectable to the external power source (such as an electricity outlet)via input circuitry or an interface such as an electrical power cable.Power circuitry QQ137 may also in certain embodiments be operable todeliver power from an external power source to power source QQ136. Thismay be, for example, for the charging of power source QQ136. Powercircuitry QQ137 may perform any formatting, converting, or othermodification to the power from power source QQ136 to make the powersuitable for the respective components of WD QQ110 to which power issupplied.

Functions implemented by some embodiments may be virtualized. In thepresent context, virtualizing means creating virtual versions ofapparatuses or devices which may include virtualizing hardwareplatforms, storage devices and networking resources. As used herein,virtualization can be applied to a node (e.g., a virtualized basestation or a virtualized radio access node) or to a device (e.g., a UE,a wireless device or any other type of communication device) orcomponents thereof and relates to an implementation in which at least aportion of the functionality is implemented as one or more virtualcomponents (e.g., via one or more applications, components, functions,virtual machines or containers executing on one or more physicalprocessing nodes in one or more networks).

In some embodiments, some or all of the functions described herein maybe implemented as virtual components executed by one or more virtualmachines implemented in one or more virtual environments hosted by oneor more of hardware nodes. Further, in embodiments in which the virtualnode is not a radio access node or does not require radio connectivity(e.g., a core network node), then the network node may be entirelyvirtualized.

The functions may be implemented by one or more applications (which mayalternatively be called software instances, virtual appliances, networkfunctions, virtual nodes, virtual network functions, etc.) operative toimplement some of the features, functions, and/or benefits of some ofthe embodiments disclosed herein. Applications are run in virtualizationenvironment which provides hardware comprising processing circuitry anda memory. The memory contains instructions executable by processingcircuitry whereby an application is operative to provide one or more ofthe features, benefits, and/or functions disclosed herein.

Virtualization of the hardware is in some contexts referred to asnetwork function virtualization (NFV). NFV may be used to consolidatemany network equipment types onto industry standard high volume serverhardware, physical switches, and physical storage, which can be locatedin data centers, and customer premise equipment.

In the following, various examples and embodiments are described thatare based on the examples and embodiments described above in the Summarysection and may be combined therewith. All the examples and embodimentspertain to RNTIs. RNTIs are identifiers used to differentiate/identify aconnected mode UE in the cell, a specific radio channel, a group of UEsin case of paging, a group of UEs for which power control is issued bythe access network node, system information transmitted for all the UEsby the access network node, and so on. There are a several RNTI types ,such as SI-RNTI, P-RNTI, C-RNTI, Temporary C-RNTI, SPS-CRNTI,TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, RA-RNTI, and M-RNTI.

FIGS. 4A and B show embodiments of a wireless device QQ110 of FIG. 3 andits functional components (that may be realized, at least in part, bythe processing circuitry QQ120). The wireless device QQ110 is configuredto determine an RA-RNTI for use in a radio network system illustrated inFIG. 3. FIG. 5 illustrates the corresponding operations in a methodembodiment.

According to the embodiment of FIG. 4A, the wireless device QQ110comprises a first counter 410 configured to be incremented after apre-defined period of time and to be re-set when having reached apredefined first number. The first counter 410 counts a first count,such as subframes. Also provided is a second counter 420 configured tobe incremented when the first counter 410 reaches the predefined firstnumber and to be re-set when having reached a predefined second number.The second counter 420 counts a second count, such as SFNs. Alsoprovided is a third counter 430 configured to be incremented when thesecond counter 420 reaches the predefined second number and to be re-setwhen having reached a predefined third number. The third counter countsa third count, such as HFNs. All the three counters 410, 420 and 430 arecontinuously operated as illustrated by step 510 in FIG. 5.

The wireless device QQ110 is configured to determine an RA-RNTI at leastbased on the second count and the third count. To this end the wirelessdevice QQ110 comprises an RA-RNTI determinator 440. This determinator440 may be triggered to determine the RN-RNTI each time it is decidedthat a random access request is to be sent by the wireless device QQ110(see steps 520 and 530, which are essentially performed in parallel withstep 510). The RA-RNTI is, for example, generated in accordance withtime and, optionally, frequency resources on which a random accessrequest message is to be sent. The corresponding triggering component isnot illustrated in FIG. 4A. When triggered, the determinator 440, inturn, triggers a random access request generator 450 to generate arandom access request message (e.g., a Random Access Preamble message)in accordance with the RA-RNTI and to send the random access requestmessage on the PRACH to the network node QQ160 of FIG. 3 in accordancewith time and, optionally, frequency resources as defined in by theRA-RNTI.

The RA-RNTI determinator 440 may be operated to determine the RA-RNTI asdescribed in greater detail above and below.

According to the embodiment of FIG. 4B, the wireless device QQ110comprises a first counting module 410′ configured to be incrementedafter a pre-defined period of time to count a first count and to bere-set when having reached a predefined first number. Also provided is asecond counting module 420′ configured to be incremented when the firstcounting module 410′ reaches the predefined first number and to bere-set when having reached a predefined second number. The secondcounting module 420′ counts a second count, such as SFNs. Also providedis a third counting module 430′ configured to be incremented when thesecond counting module 420′ reaches the predefined second number and tobe re-set when having reached a predefined third number. The thirdcounting module 430′ counts a third count, such as HFNs. All the threemodules 410′, 420′ and 430′ are continuously operated as illustrated bystep 510 in FIG. 5. The wireless device QQ110 is configured to determinean RA-RNTI at least based on the second count and the third count. Tothis end the wireless device QQ110 comprises an RA-RNTI determinationmodule 440′ that functionally corresponds to the RA-RNTI determinator440.

FIGS. 6A and 6B show embodiments of a network node QQ160 of FIG. 3 andits functional components (that may be realized, at least in part, bythe processing circuitry QQ170). The network node QQ160 is configured asan access network node configured to determine an RA-RNTI for use in aradio network system illustrated in FIG. 3. FIG. 7 illustrates thecorresponding operations in a method embodiment.

According to the embodiment of FIG. 6A, the access network node QQ160comprises a first counter 610 configured to be incremented after apre-defined period of time and to be re-set when having reached apredefined first number. The first counter 610 counts a first count,such as subframes. Also provided is a second counter 620 configured tobe incremented when the first counter 610 reaches the predefined firstnumber and to be re-set when having reached a predefined second number.The second counter 620 counts a second count, such a SFNs. Also providedis a third counter 630 configured to be incremented when the secondcounter 620 reaches the predefined second number and to be re-set whenhaving reached a predefined third number. The third counter counts athird count, such as HFNs. All the three counters 610, 620 and 630 arecontinuously operated as illustrated by step 710 in FIG. 7.

The access network node QQ160 further comprises an interface 640configured to receive a random access request message from a wirelessdevice QQ110 (step 720) via the PRACH. The access network node QQ160comprises an RA-RNTI determinator 650 configured to determine an RA-RNTIassociated with the received random access request message based on thesecond count and the third count at the time when the random accessrequest message was received at the interface 640 (step 730). TheRA-RNTI determinator 650 may be operated to determine the RA-RNTI asdescribed in greater detail above and below.

The access network node QQ160 also comprises a random access responsegenerator 660 that generates a random access response message inaccordance with the RA-RNTI as determined in step 730. The random accessresponse message is then sent via a random access response interface 670back to the wireless device QQ110. The random access response messagemay include a temporary RNTI for further use, such as a TemporaryCell-RNTI.

According to the embodiment of FIG. 6B, the access network node QQ160comprises a first counting module 610′ configured to be incrementedafter a pre-defined period of time and to be re-set when having reacheda predefined first number. The first counting module 610′ counts a firstcount, such as subframes. Also provided is a second counting module 620′configured to be incremented when the first counting module 610′ reachesthe predefined first number and to be re-set when having reached apredefined second number. The second counting module 620′ counts asecond count, such a SFNs. Also provided is a third counting module 630′configured to be incremented when the second counting module 620′reaches the predefined second number and to be re-set when havingreached a predefined third number. The third counting module 630′ countsa third count, such as HFNs. All the three counting modules 610′, 620′and 630′ are continuously operated as illustrated by step 710 in FIG. 7.

The access network node QQ160 also comprises an RA-RNTI determinationmodule 650′ configured to determine an RA-RNTI associated with thereceived random access request message based on the second count and thethird count at the time when the random access request message wasreceived (step 730). The RA-RNTI determination module 650′ may beoperated to determine the RA-RNTI as described in greater detail aboveand below.

It will be appreciated that the complete random access procedure maycomprise additional steps. As an example, the wireless device QQ110 mayrespond to the random access response message with a RRC ConnectionRequest message. The RRC Connection Request message may be sent usingthe Temporary Cell-RNTI. The access network node QQ160 may then respondwith a RRC Connection Setup message carrying an non-temporary C-RNTI.

In the following detailed embodiments, HFN count is introduced forNB-IoT UEs. HFN is a counter (sometimes also referred to as timer) atthe next level to SFN; thus RA-RNTI determination, if based upon HFN,could assist in resolving the wrap around issue and other issues, inexpanding the RA-RNTI space for NB-IoT TDD users and in sharing theexpanded RA-RNTI space. In some one of the embodiments of the presentdisclosure, it is defined that HFN is used in combination with SFN forcalculation of the RA-RNTI used for transmitting/receiving a randomaccess response.

The examples and embodiments, in particular for calculation/determiningof RA-RNTI, are in the following partially described in the context ofNB-IoT TDD, but can be applied to other radio technologies and/orsystems. The examples and embodiments can in particular be implementedin the contexts discussed above in regard to FIGS. 4 to 7, and at leastpartially within the RA-RNTI determinators 440, 650.

The examples and embodiments provide, among others, a technique for awireless device to determine the RA-RNTI used in receiving of a randomaccess response.

One example, for example performed by a wireless device QQ110, comprisesdetermining at least a part of the HFN, the SFN, and optionally acarrier id, associated with a random access transmission, determining,based on the at least a part of the HFN and the SFN (or on the HFN, theSFN and, optionally the carrier id), the RA-RNTI, and receiving, usingthe RA-RNTI, a random access response message. Receiving may compriseidentifying a specific random access response message as being addressedto the wireless device based on the associated RA-RNTI.

The present disclosure also provides a technique for a network nodeQQ160 to determine the RA-RNTI to be used in transmitting of a randomaccess response. The method comprises determining at least a part of theHFN (e.g., the third count discussed above), the SFN (e.g., the secondcount discussed above), and optionally a carrier id, associated with arandom access transmission (e.g., a received random access requestmessage), determining, based on the at least a part of the HFN and theSFN (or on the HFN, the SFN and the carrier id) the RA-RNTI, andtransmitting, using the RA-RNTI, a random access response message.

In some embodiments, the RA-RNTI is determined so that it is theequivalent of the expression:

RA-RNTI = 1 + Floor  ((SFN + (SFN MAX + 1)* mod (HFN, n))/X)

or, if the parameter carrier_id is used:

RARNTI = 1 + Floor  ((SFN + (SFN MAX + 1) * mod (HFN, n))/X) + (SFN MAX + 1) * n/X * carrier_id

wherein n can be selected as how many cycles of SFN should be comprised(a parameter sometimes also referred to as sfnCycle(s) and that can beconfigured by the upper layers), X can be selected as how compact theRA-RNTI values should be, SFNMAX is the maximum SFN value, andcarrier_id is a carrier identifier. It will be understood that theseparameters can readily be mapped on the parameters discussed in theSummary section above.

In some embodiments, the determination comprises prepending one or moreLSBs (least significant bits) of the binary representation of HFN to theMSB (most significant bit) side of the binary representation of SFN.

In some embodiments the determination comprises calculation orevaluation of a formula. Exemplary formulae are presented below:

RA-RNTI = 1 + Floor  ((SFN + (SFN MAX + 1) * mod (HFN, n))/XRA-RNTI = 1 + Floor ((SFN + (SFN MAX + 1) * mod (HFN, n))/X + (SFN MAX + 1) * n/X  * carrier_idRA-RNTI = 1 + Floor  ((SFN + 1024 * mod (HFN, n))/X) + 1024^(*)n/X * carrier_id

wherein n can be selected as how many cycles of SFN wrap around isdesired, X can be selected as how compact the RA-RNTI values should be,carrier_id is a carrier identifier, and SFNMAX is the maximum SFN value.It will be understood that these parameters can readily be mapped on theparameters discussed in the Summary section above.

Another exemplary formula is:

RA-RNTI = 1 + Floor (SFN/4 * (mod (HFN, n) + 1)) + 256 * n * carrier⁻id

wherein n can be selected as how many cycles of SFN wrap around isdesired, and carrier_id is a carrier identifier.

With the above formulae, it is possible to extend the RA-RNTI range sothat RA-RNTI wrap-around/ambiguity is avoided.

As has been explained above, in some embodiments, the RA-RNTI isdetermined so that it is the equivalent of the expression:

RA-RNTI = 1 + Floor ((SFN + (SFN MAX + 1) * mod (HFN, n))/X).

Assuming that SFNMAX is chosen to equal 1023 (e.g., as defined forNB-IoT, see also parameter c above) and X is chosen to equal 4 (seeparameter z above), this expression can be re-written as follows:

RA-RNTI = 1 + Floor  ((SFN + 1024 * mod (HFN, n))/4.

The above expression is equivalent to:

RA-RNTI = 1 + Floor  ((SFN/4 + 256 * mod (HFN, n)).

Assuming further that n is exemplarily chosen to equal 2, the aboveexpression can be re-written as follows:

RA-RNTI = 1 + Floor  ((SFN/4 + 256 * mod (HFN, 2)).

The above expression, in turn, is equivalent to:

RA-RNTI = 1 + Floor  (SFN/4) + 256 * mod (HFN, 2).

The first term in the above expression is always 1. The second term canassume any value between 0 and 255 (assuming that SFN ranges between 0and 1023, for example in an NB-IoT scenario). The third term256*mod(HFN,2) yields either 0 or 256, depending on the value of HFN.Consequently, as SFN is incremented and wraps around, leading to anincrementation of HFN, a symmetric distribution of RA-RNTI values isobtained as illustrated in FIG. 8A. Such a uniform distribution isgenerally desired to realize an efficient use of the whole range ofRA-RNTI values. Such a uniform distribution could also be obtained if nis set to, for example, 4.

In contrast, no uniform distribution is obtained for other expressionsof RA-RNTI, such as

RA-RNTI = 1 + Floor  (SFN/4) + 4096 * mod (HFN, 2).

The above expression results in a distribution having two pronouncedpeaks at the start and end of the RA-RNTI range, see FIG. 8B.

The RA-RNTI set(s) or range(s) resulting from the examples above canspan a very large range of RNTI values which can leave very few RNTIsavailable to use as, for example, C-RNTI or another RNTI type. However,all the RA-RNTI may not be used. Thus, as an embodiment, a method withina network node (e.g., the network node QQ160 discussed above), such asan access network node, is proposed as follows:

-   -   the network node determines, based on knowledge about the PRACH        configurations, which RA-RNTIs do not correspond to valid PRACH        opportunities;    -   the network node allocates (or “remaps”) RNTIs serving as        RA-RNTIs which do not correspond to valid PRACHs to RNTIs to be        used as, e.g., other types of RNTIs such as C-RNTIs, SPS-RNTIs,        etc.    -   the network node assigns allocated (“remapped”) RNTIs as, e.g.,        C-RNTIs to UEs.

The RNTI remapping mitigates or reduces C-RNTI shortage due to theRA-RNTI range expansion. When PRACH configuration is changed, thenetwork node may revoke some C-RNTIs and redo RNTI (re-)mapping.Alternatively (or as a complement) to revoking/reassigning C-RNTIs, thenetwork node could, if urgency of reconfiguration is not too high, planahead and reserve RNTIs needed for the new PRACH configuration when theyare (naturally) freed as connections are released. It should be notedthat when it herein says PRACH it may also comprise similar channelssuch as NPRACH.

The embodiments discussed above and illustrated in the drawings may inparticular be implemented in the context of NB-IoT TDD. Severalexemplary realizations of such NB-IoT TDD embodiments will now bediscussed in greater detail.

For NB-IoT wireless devices (UEs) operating in TDD mode the RA-RNTIassociated with the PRACH in which the Random Access Preamble istransmitted can be computed in accordance with any of the expressionsgiven above. For a uniform RA-RNTI distribution and an efficient use ofthe available RA-RNTI range the RA-RNTI may thus, for example, bederived using the following expression:

RA-RNTI = 1 + Floor  (SFN/4) + 256 * mod (HFN, 2).

As explained above, SFN stands for System Frame Number and, thus, forthe first radio frame of the specified PRACH. In a similar manner, HFNstands for Hyper Frame Number and, thus, for the index of the firsthyper frame of the specified PRACH. The PDCCH transmission and the PRACHresource may be on the same carrier.

The above expression, and similar expressions, are advantageous not onlyin regard to their uniform distribution of RA-RNTIs, but also in thatthe SFNs and HFNs can easily be mapped to RA-RNTI values and in that themapping is unambiguous within the SFN/HSFN range (or window).

The first releases (Rel-13 and Rel-14) of NB-IoT were only supportedwith FDD. As part of Rel-15 further NB-IoT enhancements (see RP-170732,“New WI on Further NB-IoT enhancements”, RAN #75), it has been decidedto provide support for NB-IoT TDD. In the following embodiments, theimpacts of TDD on one important functionality namely NPRACH arediscussed. Most concepts of FDD NB-IoT can be re-used for TDD, however,it is of course necessary to ensure that no additional updates areneeded for fully functioning TDD NB-IoT.

The radio resource, i.e., bandwidth (One PRB), of NB-IoT issignificantly reduced compared to other current RATs. This is to ensurean efficient system with very low power consumption and good coverage.Further, by selecting such limited bandwidth it is possible to reusespectrum previously used by GSM. Generally, repetitions are used toprovide coverage enhancements. All necessary functionality (primarilyfrom LTE) has been adapted to work for NB-IoT.

As explained previously, there is a fundamental difference between TDDand FDD, as the name implies. In FDD communication of UL and DL areseparated on different frequencies. However, in TDD mode, uplink anddownlink resources are allocated within the same frame but resources aresplit in time, see available LTE configurations in FIG. 2. NB-IoT isdeveloped to operate almost as FDD or TDD, namely with half-duplex.Similar to TDD UL and DL traffic cannot be transmitted at the same time.

The physical layer random access preambles are used by NB-IoT UEscamping on a given cell to let the base station know that the UE intendsto get access. Overall (FDD) NPRACH characteristics of exemplaryembodiments may be defined as follows:

-   -   A preamble consists of four symbol groups transmitted next to        each other using a different subcarrier per symbol group.    -   Each symbol group has a Cyclic Prefix (CP) followed by 5        symbols, the CP has different duration depending on the preamble        format.    -   Both deterministic hopping tone pattern and pseudo-random        hopping can be used.    -   The NPRACH tone spacing is 3.75 KHz.    -   A NPRACH preamble repetition unit is 5.6 ms or 6.4 ms depending        on the CP.    -   The number of repetitions can be 1, 2, 4, 8, 16, 32, 64, or 128.

The design adopted for pre-amble repetitions in FDD NB-IoT presents achallenge when adapting NPRACH for TDD NB-IoT. In principle, there is noTDD configuration that in terms of contiguous subframes in UL can hostthe NPRACH preamble repetition designed for FDD NB-IoT (i.e., thepreamble repetition unit of NPRACH goes beyond 5 ms, it can be 5.6 ms or6.4 ms depending on the CP).

The embodiments presented herein avoid wrap around issues in regard toRA-RNTI. Some embodiments are based on expression for deriving RA-RNTIthat are advantageous in regard to a uniform distribution of thecalculated RA-RNTIs. Some embodiments ensure that the SFNs and HFNs caneasily be mapped to RA-RNTI values and that the mapping is unambiguouswithin the SFN/HSFN range (or window).

While the present disclosure has been described with reference toexemplary embodiments, it will be readily apparent that the presentdisclosure may be modified in many ways. As such, the invention is onlylimited by the claims appended hereto.

ABBREVIATIONS

At least some of the following abbreviations have been used in thisdisclosure. If there is an inconsistency between abbreviations,preference should be given to how it is used above. If listed multipletimes below, the first listing should be preferred over any subsequentlisting(s).

1x RTT CDMA2000 1x Radio Transmission Technology

3GPP 3rd Generation Partnership Project

5G 5th Generation

ABS Almost Blank Subframe

ARQ Automatic Repeat Request

AWGN Additive White Gaussian Noise

BCCH Broadcast Control Channel

BCH Broadcast Channel

CA Carrier Aggregation

CC Carrier Component

CCCH SDU Common Control Channel SDU

CDMA Code Division Multiplexing Access

CGI Cell Global Identifier

CE Coverage Enhancement

CIR Channel Impulse Response

CP Cyclic Prefix

CPICH Common Pilot Channel

CPICH Ec/No CPICH Received energy per chip divided by the power densityin the band

CQI Channel Quality information

C-RNTI Cell RNTI

CSI Channel State Information

DCCH Dedicated Control Channel

DL Downlink

DM Demodulation

DMRS Demodulation Reference Signal

DRX Discontinuous Reception

DTX Discontinuous Transmission

DTCH Dedicated Traffic Channel

DUT Device Under Test

E-CID Enhanced Cell-ID (positioning method)

E-SMLC Evolved-Serving Mobile Location Centre

ECGI Evolved CGI

eNB E-UTRAN NodeB

ePDCCH enhanced Physical Downlink Control Channel

E-SMLC evolved Serving Mobile Location Center

E-UTRA Evolved UTRA

E-UTRAN Evolved UTRAN

FDD Frequency Division Duplex

FFS For Further Study

GERAN GSM EDGE Radio Access Network

gNB Base station in NR

GNSS Global Navigation Satellite System

GSM Global System for Mobile communication

HARQ Hybrid Automatic Repeat Request

HFN Hyper Frame Number

HO Handover

HSPA High Speed Packet Access

HRPD High Rate Packet Data

IoT Internet of Things

LOS Line of Sight

LPP LTE Positioning Protocol

LTE Long-Term Evolution

MAC Medium Access Control

MBMS Multimedia Broadcast Multicast Services

MBSFN Multimedia Broadcast multicast service Single Frequency Network

MBSFN ABS MBSFN Almost Blank Subframe

MDT Minimization of Drive Tests

MIB Master Information Block

MME Mobility Management Entity

MSC Mobile Switching Center

NB Narrow Band

NPBCH NP Physical Broadcast Channel

NPDCCH Narrowband Physical Downlink Control Channel

NPRACH NB-IoT PRACH

NR New Radio

NRS Narrowband Reference Signal

NSSS Narrowband Secondary Synchronization Signal

NPSS Narrowband Primary Synchronization Signal

OCNG OFDMA Channel Noise Generator

OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiple Access

OSS Operations Support System

OTDOA Observed Time Difference of Arrival

O&M Operation and Maintenance

PBCH Physical Broadcast Channel

P-CCPCH Primary Common Control Physical Channel

PCell Primary Cell

PCFICH Physical Control Format Indicator Channel

PDCCH Physical Downlink Control Channel

PDP Profile Delay Profile

PDSCH Physical Downlink Shared Channel

PGW Packet Gateway

PHICH Physical Hybrid-ARQ Indicator Channel

PLMN Public Land Mobile Network

PMI Precoder Matrix Indicator

PRACH Physical Random Access Channel

PRS Positioning Reference Signal

PSS Primary Synchronization Signal

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RACH Random Access Channel

QAM Quadrature Amplitude Modulation

RAN Radio Access Network

RA Random Access

RA-RNTI Random Access Resource Radio Network Temporary Identifier

RAT Radio Access Technology

RLM Radio Link Management

RNC Radio Network Controller

RNTI Radio Network Temporary Identifier

RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RSCP Received Signal Code Power

RSRP Reference Symbol Received Power OR Reference Signal Received Power

RSRQ Reference Signal Received Quality OR Reference Symbol Received

Quality

RSSI Received Signal Strength Indicator

RSTD Reference Signal Time Difference

SCH Synchronization Channel

SCell Secondary Cell

SDU Service Data Unit

SFN System Frame Number

SGW Serving Gateway

SI System Information

SIB System Information Block/System Information Broadcast

SNR Signal to Noise Ratio

SON Self Optimized Network

SS Synchronization Signal

SSS Secondary Synchronization Signal

TDD Time Division Duplex

TDOA Time Difference of Arrival

TOA Time of Arrival

TSS Tertiary Synchronization Signal

TTI Transmission Time Interval

UE User Equipment

UL Uplink

UMTS Universal Mobile Telecommunication System

USIM Universal Subscriber Identity Module

UTDOA Uplink Time Difference of Arrival

UTRA Universal Terrestrial Radio Access

UTRAN Universal Terrestrial Radio Access Network

WCDMA Wide CDMA

WLAN Wide Local Area Network

REFERENCES

[1] Y. P. E. Wang, X. Lin, A. Adhikary, A. Grovlen, Y. Sui, Y.Blankenship, “J. Bergman, and H. S. Razaghi, “A primer on 3GPPnarrowband internet of things,” IEEE Commun. Mag., vol. 53, no. 3, pp.117-123, March 2017.

[2] RP-170732, “New WI on Further NB-IoT enhancements”, RAN #75.

[3] 3GPP, 36.321ve30 “Medium Access Control (MAC) protocolspecification”, 2017-June and/or 2017-July

[4] 3GPP TS 36.211, “Physical channels and modulation”, v14.2.0.

What is claimed is:
 1. A wireless device configured to determine aRandom Access-Radio Network Temporary Identifier (RA-RNTI) for use in aradio network system, wherein the wireless device comprises: a firstcounter configured to be incremented after a pre-defined period of timeand to be re-set when having reached a predefined first number, whereinthe first counter counts a subframe number; a second counter configuredto be incremented when the first counter reaches the predefined firstnumber and to be re-set when having reached a predefined second number,wherein the second counter counts a system frame number (SFN_id); and athird counter configured to be incremented when the second counterreaches the predefined second number and to be re-set when havingreached a predefined third number, wherein the third counter counts ahyper frame number, H-SFN; and wherein the wireless device is configuredto determine an RA-RNTI based on a mathematical formula that includesboth the SFN_id and the H-SFN, wherein the mathematical formula isRA-RNTI = 1 + floor  (SFN_id/4) + 256 * mod (H-SFN, 2)
 2. The wirelessdevice of claim 1, wherein the RA-RNTI identifies at least a timeresource for transmission of a random access message by the wirelessdevice.
 3. The wireless device of claim 1, configured to determine theRA-RNTI responsive to a decision that a random access is to beperformed.
 4. The wireless device of claim 1, configured to perform atleast one of the following: generating a random access request messagein accordance with the RA-RNTI and send the random access requestmessage towards an access network; identifying a random access responsemessage from the access network associated with the RA-RNTI.
 5. Thewireless device of claim 1, wherein the wireless device is a NarrowbandInternet of Things User Equipment (NB-IoT) UE, configured to determinethe RA-RNTI for a Time Division Duplex (TDD) mode.
 6. A radio networksystem including the wireless device of claim
 1. 7. An access networknode configured to determine a Random Access-Radio Network TemporaryIdentifier (RA-RNTI) for use in a radio network system, the accessnetwork node comprising: a first counter configured to be incrementedafter a pre-defined period of time and to be re-set when having reacheda predefined first number, wherein the first counter counts a subframenumber; a second counter configured to be incremented when the firstcounter reaches the predefined first number and to be re-set when havingreached a predefined second number, wherein the second counter counts asystem frame number, SFN_id; a third counter configured to beincremented when the second counter reaches the predefined second numberand to be re-set when having reached a predefined third number, whereinthe third counter counts a hyper frame number, H-SFN; an interfaceconfigured to receive a random access message from a wireless device;and wherein the access network node is configured to determine anRA-RNTI associated with the random access message based on amathematical formula that includes both the SFN_id and the H-SFN at thetime when the random access message was received, wherein themathematical formula isRA-RNTI = 1 + floor  (SFN⁻id/4) + 256  * mod (H-SFN, 2).
 8. The accessnetwork node of claim 7, configured to generate a random access responsethat includes the RA-RNTI and send the random access response to thewireless device.
 9. The access network node of claim 7, configured tomanage a first RNTI type comprising a number of designated RA-RNTIsavailable for use in the radio network system and at least one secondRNTI type different from the first type; determine, based on apriori-knowledge, one or more designated RA-RNTIs available but unusedin the radio network system; and allocate the one or more unuseddesignated RA-RNTIs to the second RNTI type.
 10. The access network nodeof claim 9, wherein the a priori-knowledge relates to communicationopportunities on a transmission channel.
 11. The access network node ofclaim 7, configured to determine the RA-RNTI for a Time Division Duplex(TDD) mode.
 12. A radio network system including the access network nodeof claim
 7. 13. A method of determining a Random Access-Radio NetworkTemporary Identifier (RA-RNTI) for use in a radio network system, themethod being performed by a wireless device and comprising: operating afirst counter configured to be incremented after a pre-defined period oftime and to be re-set when having reached a predefined first number,wherein the first counter counts a subframe number; operating a secondcounter configured to be incremented when the first counter reaches thepredefined first number and to be re-set when having reached apredefined second number, wherein the second counter counts a systemframe number, SFN_id; and operating a third counter configured to beincremented when the second counter reaches the predefined second numberand to be re-set when having reached a predefined third number, whereinthe third counter counts a hyper frame number, H-SFN; and determining anRA-RNTI based on a mathematical formula that includes both the SFN_idand the H-SFN, wherein the mathematical formula isRA-RNTI = 1 + floor  (SFN⁻id/4) + 256  * mod (H-SFN, 2).
 14. The methodof claim 13, wherein the RA-RNTI identifies at least a time resource fortransmission of a random access message by the wireless device.
 15. Themethod of claim 13, wherein said determining the RA-RNTI is responsiveto a decision that a random access is to be performed.
 16. The method ofclaim 13, further comprising at least one of the following: generating arandom access request message in accordance with the RA-RNTI and sendthe random access request message towards an access network; andidentifying a random access response message from the access networkassociated with the RA-RNTI.
 17. A method of determining a RandomAccess-Radio Network Temporary Identifier (RA-RNTI) for use in a radionetwork system, the method being performed by an access network node andcomprising: operating a first counter configured to be incremented aftera pre-defined period of time and to be re-set when having reached apredefined first number, wherein the first counter counts a subframenumber; operating a second counter configured to be incremented when thefirst counter reaches the predefined first number and to be re-set whenhaving reached a predefined second number, wherein the second countercounts a system frame number, SFN_id; operating a third counterconfigured to be incremented when the second counter reaches thepredefined second number and to be re-set when having reached apredefined third number, wherein the third counter counts a hyper framenumber, H-SFN; receiving a random access message from a wireless device;and determining an RA-RNTI associated with the random access messagebased on a mathematical formula that includes both the SFN_id and theH-SFN at the time when the random access message was received, whereinthe mathematical formula isRA-RNTI = 1 + floor  (SFN⁻id/4) + 256  * mod (H-SFN, 2).
 18. The methodof claim 17, further comprising: generating a random access responsethat includes the RA-RNTI; and sending the random access response to thewireless device.
 19. The method of claim 17, further comprising:managing a first RNTI type comprising a number of designated RA-RNTIsavailable for use in the radio network system and at least one secondRNTI type different from the first type; determining, based on apriori-knowledge, one or more designated RA-RNTIs available but unusedin the radio network system; and allocating the one or more unuseddesignated RA-RNTIs to the second RNTI type.
 20. The method of claim 17,wherein the a priori-knowledge relates to communication opportunities ona transmission channel.